latest 16 messages by novas0x2a|laptop

+ [2016-12-07T19:20:39Z] novas0x2a|laptop i was curious if the remote ref namespace was documented anywhere? (like, refs/pulls/*); more specifically, i was hoping there was a ref namespace devoted only to open pull requests :)
+ [2015-07-17T00:41:53Z] novas0x2a|laptop is there a reliable way to get closed_by information for a pull via the api? it doesn't look like that field is usually populated for pulls, for some reason (even though it's reported via the web).
+ [2015-01-09T21:12:24Z] novas0x2a|laptop github doesn't support that level of granularity, no
+ [2014-12-20T00:24:45Z] novas0x2a|laptop and i don't feel like using my api allocation to show that github has a bug, when i've already figured out how to work around the bug
+ [2014-12-20T00:23:27Z] novas0x2a|laptop description of X-RateLimit-Reset: "The time at which the current rate limit window resets in UTC epoch seconds."
+ [2014-12-20T00:22:16Z] novas0x2a|laptop you're right, it doesn't; the world only makes sense if i assume that the documentation is wrong and github is returning the tz in pacific time.
+ [2014-12-20T00:19:41Z] novas0x2a|laptop (that was sarcasm; if i interpret the timestamp the way the doc says to, it puts the rate limit expiration in the past)
+ [2014-12-20T00:18:56Z] novas0x2a|laptop events represented in some interfaces but not others, pagination pages for things returning partial information
+ [2014-12-20T00:16:56Z] novas0x2a|laptop man, there are so many bugs with the api it's not really worth filing bugs for them
+ [2014-12-20T00:13:54Z] novas0x2a|laptop unless my rate limit window refreshes 8 hours ago :)
+ [2014-12-20T00:13:00Z] novas0x2a|laptop X-RateLimit-Reset says that it returns the reset window in UTC epoch seconds, but it appears to be in my local time zone (which i suspect means it's actually returning server local timezone)